CDISC Builder™  2.1 - Installation Test Scripts - Findings
The following documentation contains test scripts and expected results for validating the CDISC Builder Findings tool.  Do the following to verify proper installation:
  • Perform each test by performing the steps specified by the instructions.  
  • Evaluate the results of each step by comparing them with results described in the Documentation column. 
Script Description Documentation
findings1.sas Test the condition where the required parameters are missing. Instructions 1

findings1.log
findings2.sas Test the condition where the parameters: data, rdomain, usubjid, testvars and  varname  are invalid. Instructions 2

findings2.log

 
findings3a.sas
findings3b.sas 		Test the condition where the basecode is invalid. Instructions 3

findings3a.log

findings3b.log
findings4a.sas
findings4b.sas
findings4c.sas
  		Verify that output dataset is generated with or without output parameter and if output parameter is one level or two level names.  Instructions 4
findings5.sas Verify that basecode is generated. 

Instructions 5

f_basecode5.sas
findings6.sas Verify that repeated data is transposed with or without 'YES'.

Instructions 6

findings6.log

Instructions 1
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation directory named "saspgm".

  2. Right mouse click on findings1.sas and select "Batch Submit".

  3. Review the findings1.log and verify that the following messages are produce corresponding to each test.

    • ERROR: [findings] is missing required parameter DATA. 

    • ERROR: [findings] is missing required parameter STUDYID.

    • ERROR: [findings] is missing required parameter RDOMAIN.

    • ERROR: [findings] is missing required parameter USUBJID.

    • ERROR: [findings] is missing required parameter VARNAME.

Instructions 2
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the validation directory named "saspgm".

  2. Right mouse click on findings2.sas and select "Batch Submit".

  3. Review the findings2.log and verify that the following messages are produce corresponding to each test.

    • ERROR: [findings] has an invalid dataset specified by DATA. 

    • ERROR: [findings] contains an invalid related domain: AZ 
      NOTE: valid related domain include: AU, BM, BR, CP, DC, DR, DV, DY, EE, EG, HU, IE, IM, LB, MB, 
      NE, OM, PC, PE, PP, QS, SC, SK, SL, ST, VS. 

    • ERROR: [findings] has an invalid value specified by USUBJID. 

    • ERROR: [findings] the variable TESTVAR3 specified in TESTVAR is an invalid variable. 

    • ERROR: [findings] the variable VAR4 specified in VARNAME is an invalid variable. 

Instructions 3
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the data directory named "data\findings".

  2. Remove dataset AU if existed.

  3. Navigate to the validation directory named "saspgm".

  4. Right mouse click on findings3a.sas and select "Batch Submit".

  5. Review the findings3a.log and verify that the following messages are produce corresponding to each test.

    • WARNING: [findings] base code file path does not exist.  

  6. Navigate to the data directory named "data\findings".

  7. Verify that dataset AU was created, and remove it.

  8. Navigate to the validation directory named "saspgm".

  9. Right mouse click on findings3b.sas and select "Batch Submit".

  10. Review the findings3b.log and verify that the following messages are produce corresponding to each test.

    • WARNING: [findings] base code file name is invalid.

Instructions 4
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the data directory named "data\findings".

  2. Remove dataset AU if existed.

  3. Navigate to the validation directory named "saspgm".

  4. Right mouse click on findings4a.sas and select "Batch Submit".

  5. Review the findings4a.log and verify that there is no error message.

  6. Navigate to the data directory named "data\findings".

  7. Verify that dataset AU was generated and remove it.

  8. Navigate to the validation directory named "saspgm".

  9. Right mouse click on findings4b.sas and select "Batch Submit".

  10. Review the findings4b.log and verify that there is no error message.

  11. Navigate to the data directory named "data\findings".

  12. Verify that dataset AU was generated and remove it.

  13. Navigate to the validation directory named "saspgm".

  14. Right mouse click on findings4c.sas and select "Batch Submit".

  15. Review the findings4c.lod and verify that there is no error message.

  16. Navigate to the data directory named "data\findings".

  17. Verify that dataset AU was generated.

Instructions 5
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the data directory named "data\findings".

  2. Delete dataset AU if existed.

  3. Navigate to the validation directory named "saspgm".

  4. Right mouse click on findings5.sas and select "Batch Submit".

  5. Review the findings5.log and verify that there is no error message.

  6. Verify that basecode5.sas is generated.

Instructions 6
The following instructions are accomplished through Windows Explorer.

  1. Navigate to the data directory named "data\findings".

  2. Delete dataset AU if existed.

  3. Open dataset FINDINGS and verify that there is repeated data.

  4. Navigate to the validation directory named "saspgm".

  5. Right mouse click on findings6.sas and select "Batch Submit".

  6. Review the findings6.log and verify that there is no error message.

  7. Navigate to the data directory named "data\findings".

  8. Open dataset AU and verify that repeated data was transposed.

  9. Open dataset OM and verify that repeated data was transposed with the variable's label where value is "yes".

For more information, please contact MXI .

 
     Meta-Xceed Inc. © 2009